Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Malware protection 5: Refactor Special Error Types #3642

Merged
merged 7 commits into from
Dec 3, 2024

Conversation

mallexxx
Copy link
Collaborator

Task/Issue URL: https://app.asana.com/0/481882893211075/1208033567421351/f
BSK PR: duckduckgo/BrowserServicesKit#1098
macOS PR: duckduckgo/macos-browser#3603

Description:

  • Update Error Data type to match macOS

Steps to test this PR:

  1. Validate on badssl.com that bad SSL error handling works as before and error page + bypass works

Definition of Done (Internal Only):

Copy Testing:

  • Use of correct apostrophes in new copy, ie rather than '

Orientation Testing:

  • Portrait
  • Landscape

Device Testing:

  • iPhone SE (1st Gen)
  • iPhone 8
  • iPhone X
  • iPhone 14 Pro
  • iPad

OS Testing:

  • iOS 15
  • iOS 16
  • iOS 17

Theme Testing:

  • Light theme
  • Dark theme

Internal references:

Software Engineering Expectations
Technical Design Template

mallexxx added a commit to duckduckgo/BrowserServicesKit that referenced this pull request Dec 3, 2024
<!--
Note: This checklist is a reminder of our shared engineering
expectations.
-->

Please review the release process for BrowserServicesKit
[here](https://app.asana.com/0/1200194497630846/1200837094583426).

**Required**:

Task/Issue URL:
https://app.asana.com/0/481882893211075/1208033567421351/f
iOS PR: duckduckgo/iOS#3642
macOS PR: duckduckgo/macos-browser#3603
What kind of version bump will this require?: Major

**Description**:
- Some final adjustments for Malware protection integration and Privacy
Dashboard protocol change: refactor `SSLErrorType`, `SpecialErrorData`

<!--
Tagging instructions
If this PR isn't ready to be merged for whatever reason it should be
marked with the `DO NOT MERGE` label (particularly if it's a draft)
If it's pending Product Review/PFR, please add the `Pending Product
Review` label.

If at any point it isn't actively being worked on/ready for
review/otherwise moving forward (besides the above PR/PFR exception)
strongly consider closing it (or not opening it in the first place). If
you decide not to close it, make sure it's labelled to make it clear the
PRs state and comment with more information.
-->

**Steps to test this PR**:
1. Validate SSL cert error page and bypassing works
(https://badssl.com/)
2. Validate Phishing detection works
(http://privacy-test-pages.site/security/badware/phishing.html) – enable
Feature Flag in Debug -> Feature flags for it to work

<!--
Before submitting a PR, please ensure you have tested the combinations
you expect the reviewer to test, then delete configurations you *know*
do not need explicit testing.

Using a simulator where a physical device is unavailable is acceptable.
-->

**OS Testing**:

* [ ] iOS 14
* [ ] iOS 15
* [ ] iOS 16
* [ ] macOS 10.15
* [ ] macOS 11
* [ ] macOS 12

---
###### Internal references:
[Software Engineering
Expectations](https://app.asana.com/0/59792373528535/199064865822552)
[Technical Design
Template](https://app.asana.com/0/59792373528535/184709971311943)
@mallexxx mallexxx merged commit 0e22335 into alex/malware-protection Dec 3, 2024
13 checks passed
@mallexxx mallexxx deleted the alex/malware-protection-5 branch December 3, 2024 11:55
mallexxx added a commit to duckduckgo/BrowserServicesKit that referenced this pull request Dec 3, 2024
…tion (#1091)

Task/Issue URL: https://app.asana.com/0/1202406491309510/1208033567421351/f
iOS PR: duckduckgo/iOS#3642
macOS PR: duckduckgo/macos-browser#3588

**Description**:
- Renamed `PhishingDetection` to `MaliciousSiteProtection`
- Adjusted and cleaned up some code parts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants